Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

Overview

The Customization Manager coordinates the application of UI customizations to your application. The manager retrieves a priority list for the session and uses it to determine the order in which customizations should be applied. It then builds and caches a set of customization codes that apply to the current client session. When the client requests information from the Repository Manager, the customization codes are used to retrieve and properly display the correct objects.

In a distributed environment, the Customization Manager is started on both the client and server sides. There is a wrapper program for each side that sets the global variable, server-side, to either YES for the server-side version or NO for the client-side version. Both programs then include the main code of the manager from the ry\app\rycusmngrp.i include file. The differences in how the manager operates on each side are triggered by checking the value of the server-side variable.

You can retrieve the handle of the Customization Manager by running the following code:

ASSIGN hCustomizationManager = DYNAMIC-FUNCTION("getManagerHandle":U, INPUT "CustomizationManager":U).

Table 3–1 shows the files that contain the Customization Manager’s code.

Table 3–1: Customization Manager files

Type	Path
Client-side wrapper	ry\app\rycusclntp.p
Server-side wrapper	ry\app\rycussrvrp.p
Main code	ry\app\rycusmngrp.i
Included files	adm2\globals.i ry\app\rydefrescd.i

For more information on this Manager, see the chapter on using the Progress Dynamics Managers in OpenEdge Development: Progress Dynamics Advanced Development .